2013-07-19 - 6651 - Spec - Oops Enhancements-Commodity Codes #US #materialmaster #ABAPLSMW
SPECIFICATIONS
6651.100 - Spec- Oops Enhancements - Commodity Codes
Purpose
Oops Enhancements - Commodity Codes
To ensure global custom compliance by assigning proper commodity codes for material.
Admin Info
Purpose
|
Oops Enhancements - Commodity Codes
|
Requested By
|
Babu Lankipalli
|
Spec Created By
|
Adithya
|
Spec Created Date
|
07/19/2013
|
Spec QA by
|
Adithya
|
Objects
|
ZCOMMODITY_CODES
ZMM_COMMODITY
|
Document Status
|
Complete
|
References
Prior Tickets
2013-06-28 - Procedure - 6651.100 - Ops Enhancements - Commodity Codes
Documents
Project Spec Commodity Codes 07182013.docx
Functional Requirement
Ensure global customs compliance by assigning proper commodity codes for materials.
Provide visibility to correct commodity codes on customs / shipping documentation leading to correct import duty calculations and faster customs processing times.
Set foundation to calculate correct standard costs based on proper import duties.
Provide foundation for correct Indra-stat report in EMEA.
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
1. Created transaction to maintain FCC Code, Silhouette, plant and corresponding commodity codes.
2. Update Material creation program logic to read corresponding commodity codes from master table while materials are created.
Test Plan
|
Test Scenario
|
Expected Results
|
1
|
Create the Z Master Table to maintain the combination of Commodity codes
|
The combination maintained must be displayed in the master table
|
2
|
When Material Master is created
|
Correct commodity code must be picked
|
Solution Details
Master table did not find corresponding commodity code:
Manual material upload file process by engineering team:
- If commodity code is not found, users will get error in simulation mode and therefore they will not create materials until customs compliance team maintain necessary data.
Automated material upload file process (ROAL, MCP):
- Automated material upload file process (ROAL, MCP):
- Materials will not be created and SAP materials creation job will fail.
- ROAL materials creation has exception report.
- Design exception report for MCP materials creation similar to ROAL.
Alternative solutions considered/Limitations:
- Maintain master table in non-SAP application (SQL): Material creation programs in SAP will not read data from non-SAP application.
- Get commodity codes from MCP: If commodity codes master data table is maintained in MCP application then upload file from MCP application will be good for materials creating through MCP. But the ROAL, Cap-machine, material creation sheet from engineering (head wear, apparel) and material extensions will not work.
LIST OF LSMW'S:
a) For Apparel Materials
Project : ZGBLUPLOAD
Sub-project: FERT
Object: EXTENSION_APP
b) For Regular Materials
Project : ZGBLUPLOAD
Sub-project: FERT
Object: EXTENSION
c) For Engineering Materials
Project : ENGINEERING
Sub-project: FERT
Object: EXTENSION
d) For Existing Materials
Project : MATERIAL_EXT
Sub-project: MATERIAL_EXT
Object: GLOBAL
Above are the LSMW's in which we are maintaining commodity codes .
All commodity codes are fetched from Z TABLE (ZMM_COMMODITY) .
LOGIC FOR COMMODITY:
Created transaction (ZMM_COMMODITYCODES) to maintain FCC Code, Silhouette, plant and corresponding commodity codes.
Fetching commodity codes based on below conditions. If below conditions does not satisfies then we are throwing Error Message while Running in simulation mode.
a)source country : Coming from vendor in input of lsmw creation .
b)FCC code:fabric Content code from input file of lsmw .
c)plant country:Based on material plant .
Issues
2013-08-08 - 6651.1000 - Rel Notes - Ops Enhancements - Commodity Codes
2013-08-26 - 6651.100 - Rel Notes - Oops Enhancements - Commodity Codes - 1
2013-11-14 - 6651.100 - Rel Notes - Oops Enhancements - Commodity Codes - 3